home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 21
/
Cream of the Crop 21 (Terry Blount) (October 1996).iso
/
comm
/
wv32i998.zip
/
README.TXT
< prev
next >
Wrap
Text File
|
1996-08-31
|
49KB
|
1,086 lines
*** NOTE NOTE NOTE ***
WinVN 0.99-8 (Released version)
Make sure to read the Installation Instructions before installing
WinVN. E-mail traffic is high for the unpaid supporters of this
product, and almost all the questions people ask are either answered
in this README.TXT, FAQ.TXT, the WWW site, the hardcopy docs or the
MAIL.WINVN newsgroup on NEWS.KSC.NASA.GOV. Please help us spend our
time making WinVN a better product and not answering the same
questions over and over.
JD
8/31/96
**********************
Contents
========
What is WinVN?
Requirements
Upgrade Instructions
New Installation Instructions
WinVN Files
Latest Version
Contacting the Developers
Credits
Revision History
What is WinVN?
==============
WinVN is an NNTP newsreader for the Microsoft Windows family. You can use
it to read and post Usenet News, and send email via the SMTP or MAPI
protocols. There are three version of WinVN all derived from a common
set of source files:
WinVN 16-bit For Windows and Windows for Workgroups
WinVN 32-bit *Only* for Windows NT and Windows 95
WinVN AXP *Only* for Windows NT on DEC Alpha platform
Requirements
============
1) An appropriate operating system: Windows, Windows for Workgroups,
Windows NT, Windows NT/AXP or Windows 95.
2) A correct installation as described below.
3) An appropriate network connection with a TCP/IP stack and either a
WINSOCK.DLL or a WSOCKETS.DLL. See Installation Instructions below.
4) An NNTP News Server that supports at least one of the following NNTP
extensions:
XHDR Most news servers can do this
XOVER INN is a news server that does XOVER
WinVN will use XOVER, a better protocol, if your server supports it.
You need the name or address of the server. A few news servers require
a username and password for authentication--most do not. Contact your
news server's administrator if in doubt. Do NOT fill out the
authentication field unless you are sure your news provider requires
it.
Upgrade Intructions
===================
1) Just unzip the archive into your current WinVN directory. The archive does
not contain NEWSRC or WINVN.INI files, so your existing settings will be
preserved and WinVN will merge in any new features needed for the new
release. (If you are paranoid: move your WINVN.INI and NEWSRC files to
a different directory, delete everything else in your WinVN directory,
unzip WinVN, and finally move your WINVN.INI and NEWSRC files back.)
2) *** IF THE INCLUDED CTL3D DLL IS A NEWER VERSION THAN YOURS ***
WinVN 16-bit:
Move (*don't copy*) CTL3DV2.DLL into your \WINDOWS\SYSTEM directory.
There must be *one and only one* instance of this file on your disk!
If you have more than one copy in your search path, the DLL will
give you a non-fatal warning message that it is installed incorrectly.
WinVN 32-bit:
Windows NT:
Move (*don't copy*) CTL3D32.DLL into your %SystemRoot%\SYSTEM32 directory.
Windows 95:
Move (*don't copy*) CTL3D32.DLL into your \WINDOWS\SYSTEM directory.
There must be *one and only one* instance of this file on your disk!
New Installation Instructions
=============================
0) Read this file, the help file, and the FAQ. They will answer most of
your questions.
1) Create a WinVN directory and unzip the archive into this directory.
2) *** DO NOT SKIP THIS STEP! ***
WinVN 16-bit:
If CTL3DV2.DLL doesn't exist on your system or if it is newer
than the one in your Windows System directory,
Move (*** DO NOT COPY!!! ***) CTL3DV2.DLL into your
\WINDOWS\SYSTEM directory. There must be *one and only one*
instance of this file on your disk! or you will get a
CTL3DV2.DLL was not installed correctly message. This message
is put out by the authors of CTL3DV2.DLL and not by WinVN! We
can't do anything about that. If you don't use the CTL3DV2.DLL
in the WinVN distribution, rename it or delete it out of your
WinVN directory.
WinVN 32-bit:
Windows NT:
If you don't have CTL3D32.DLL or if the one in WinVN is newer
than the version you have, Move (*don't copy*) CTL3D32.DLL into
your %SystemRoot%\SYSTEM32 directory. If you don't use the
CTL3DV232.DLL in the WinVN distribution, rename it or delete it out
of your WinVN directory.
Windows 95:
If you don't have a CTL3D32.DLL in your Windows area, move
(*don't copy*) CTL3D32.DLL into your \WINDOWS\SYSTEM directory.
If you don't use the CTL3DV232.DLL in the WinVN distribution,
rename it or delete it out of your WinVN directory.
There must be *one and only one* instance of this file on your disk!
(Note: if you are running Windows 3.1 with Win32S, you still can't
run the 32-bit version of WinVN. Win32S doesn't provide a 32-bit
WINSOCK.DLL so it won't buy you anything even if we supported it.)
3) This is very important! Choose the appropriate WinSock interface by
editing the GenSockDLL entry in the Communications section of your
WINVN.INI. WinVN doesn't ship with a WINVN.INI file but it will
produce one the first time you run the program. If you want to
change WinVN's DLL that interfaces to the WINSOCK.DLL on your
networking stack, run WinVN first, have it produce a WINVN.INI
and then edit the WINVN.INI using an editor. Note: the GenSockDLL
is not a replacement for the WinSock provided by your networking
vendor so don't try editing WinVN.INI and replace the GenSockDLL line
in the INI file with a WinSock.DLL. The GenSockDLL entry is the
interface library that WinVN uses to call your WinSock.DLL.
See below for details.
WinVN 16-bit:
GWINSOCK.DLL The default, which should work in most cases
PWKSOCK.DLL For pre-WinSock 1.1 compliant TCP/IP stacks
such as Dec Pathworks 4.1 or earlier (Pathworks
5.0 or higher use GWINSOCK.DLL) or LanManager 2.1a
or earlier. (LanMan 2.2 or higher, use GWINSOCK.DLL)
GENASYNC.DLL Faster with modem and Trumpet or NetManage products
WinVN 32-bit:
GWINSOCK.DLL The default, which should work in all cases
Details
-------
You will have one of the following two types of TCP/IP stacks:
WinSock v1.1 (or higher) TCP/IP stack and WINSOCK.DLL:
(Examples: Microsoft TCP/IP, Trumpet, PC/TCP, Windows NT,
Windows 95, NetManage TCP/IP, LanManager 2.2, DEC Pathworks 5.1)
a) Make sure WINSOCK.DLL is in your path before starting Windows.
b) Make sure the GenSockDLL entry in the Communications section
of your WINVN.INI is set to GWINSOCK.DLL or GENASYNC.DLL, as
appropriate.
SPECIAL NOTE: If you are using later versions of the Trumpet or
NetManage (Chameleon) products, you will get better performance over
a modem with GENASYNC.DLL rather than GWINSOCK.DLL.
*or*
Pre-WinSock v1.1 TCP/IP stack and WSOCKETS.DLL:
(Examples: DEC Pathworks 4.1 or Microsoft LanManager 2.1a)
a) Make sure WSOCKETS.DLL is in your path before starting Windows.
b) Make sure the GenSockDLL entry in the Communications section
of your WINVN.INI is set to PWKSOCK.DLL.
NOTE: GWINSOCK.DLL, GENASYNC.DLL and PWKSOCK.DLL are not replacements
for your TCP/IP stack's own socket DLLs--they use them. For example,
GWINSOCK.DLL talks to WINSOCK.DLL, and PWKSOCK.DLL talks to WSOCKETS.DLL.
4) Configure the Communications Options. The first time you start WinVN
you will be asked to configure these options. You must have the name or
address of your news server. The TCP port should be NNTP or 119 if the
former does not work. The Username and Password sh